Governs how the triggers for immediate updating subscriptions execute calls at the publisher 參數控制即時更新訂閱的觸發器如何在發布服務器上執行調用。
Subscriber , distributor , and publisher are connected most of the time for immediate updating subscriptions 大多數情況下,訂閱服務器、分發服務器和發布服務器都是相互連接的(適用于立即更新訂閱) 。
Subscribers to oracle publications cannot use immediate updating or queued updating subscriptions , or be nodes in a peer - to - peer or bidirectional topology Oracle發布的訂閱服務器不能使用立即更新訂閱或排隊更新訂閱,也不能作為對等或雙向拓撲中的節點。
If immediate updating or queued updating options are used with transactional replication , updates can be made at the subscriber , and with queued updating , conflicts might occur 如果事務性復制使用了立即更新或排隊更新選項,更新可以在訂閱服務器中進行,對于排隊更新,可能會發生沖突。
Because changes to the data must be made at the publisher when transactional replication is used without immediate updating or queued updating options , update conflicts are avoided 由于數據更改必須在發布服務器中進行(使用事務性復制時,無需指定立即更新或排隊更新選項) ,從而避免了更新沖突。
Therefore , oracle publishing does not support : publications with immediate updating or queued updating subscriptions ; or topologies in which publication tables also act as subscription tables , such as peer - to - peer and bidirectional replication 因此, oracle發布不支持以下功能:包含立即更新訂閱或排隊更新訂閱的發布;或者其中發布表還作為訂閱表的拓撲,例如,對等和雙向復制。
It does support queued updating using push subscriptions and immediate updating using push or pull subscriptions immediate updating requires that microsoft distributed transaction coordinator ms dtc be running on the same computer as the sse instance Sse確實支持使用推送訂閱進行排隊更新,并且支持使用推送或請求訂閱進行立即更新(立即更新需要在運行sse實例的計算機上運行microsoft分布式事務處理協調器( msdtc ) ) 。